Values and Sized types are not larger than isize::MAX#2202
Open
joshlf wants to merge 4 commits intorust-lang:masterfrom
Open
Values and Sized types are not larger than isize::MAX#2202joshlf wants to merge 4 commits intorust-lang:masterfrom
Sized types are not larger than isize::MAX#2202joshlf wants to merge 4 commits intorust-lang:masterfrom
Conversation
Contributor
Author
Co-authored-by: Jacob Lifshay <programmerjake@gmail.com>
Sized types are not larger than isize::MAXSized types are not larger than isize::MAX
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
See #t-opsem > Constraints on abstract values? @ 💬 for context.
For
Sizedtypes, we nearly already guarantee this by implication. If we assume thatLayout::new<T>() -> Layoutcan't fail to compile or panic at runtime, then it implies that, for anyT: Sized, it is possible to acquire aLayoutdescribing thatT.Layout, in turn, guarantees that:This is also already guaranteed for any Rust allocation, although in theory it's possible that: